-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-7.0] use group secret for GetGroupSnapshotStatus #1057
Conversation
GetGroupSnapshotStatus is a group operation on a specific group with an ID, we can use the group specific secret instead of List specific secret. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> (cherry picked from commit b2447a0)
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Madhu-1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @Madhu-1. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @xing-yang |
/ok-to-test |
@xing-yang is this good to get merged? |
@Madhu-1 We are going to cut a new release soon. I wonder if we still need to patch this in 7.0 branch. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
GetGroupSnapshotStatus is a group operation on a specific group with an ID, we can use the group specific secret instead of List specific secret.
Signed-off-by: Madhu Rajanna madhupr007@gmail.com
(cherry picked from commit b2447a0)
backport of #1051
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: